Can you get Basline info without having the Module open?

Is is possible to get any information about the Baselines, without having the Module open?

It looks like you can get a handle using: baseline(ModuleVersion modver)

However, in order to get modver, you'd need to use something like: moduleVersion(ModName_ modRef,Baseline b)

I'm looking for something like: for Baseline in Module do {}, but without needing the module open.
djakad - Mon Mar 23 14:22:02 EDT 2009

Re: Can you get Basline info without having the Module open?
ePiallat - Tue Mar 24 04:52:42 EDT 2009

I'm afraid there is no solution, at least up to DOORS 8.2. (I can't test newer versions from here)

There are only two "Baseline" loops:
for Baseline in Module do {}
for Baseline in all Module do {}
// btw I don't know what's the difference between iterating through "all" the Module and through the Module itself
And by searching for some "for ModuleVersion in ModName_ do" loop, or "for string in baselines ModName_ do" loop, I only found this error message hard-coded in DOORS binary:

Baseline information must be accessed by "for Baseline in Module" iterator.

– Éric

Re: Can you get Basline info without having the Module open?
djakad - Tue Mar 24 11:33:36 EDT 2009

ePiallat - Tue Mar 24 04:52:42 EDT 2009
I'm afraid there is no solution, at least up to DOORS 8.2. (I can't test newer versions from here)

There are only two "Baseline" loops:
for Baseline in Module do {}
for Baseline in all Module do {}
// btw I don't know what's the difference between iterating through "all" the Module and through the Module itself
And by searching for some "for ModuleVersion in ModName_ do" loop, or "for string in baselines ModName_ do" loop, I only found this error message hard-coded in DOORS binary:

Baseline information must be accessed by "for Baseline in Module" iterator.

– Éric

Eric, I think you are right. I tried and tried to find other methods. But, it seems the only way is the "for baseline in module" loop, which requires the module to be open. Also, in the DXL manual, for related commands such as major(), minor(), suffix(), annotation(), etc., it states that these commands "must be used in a for baseline in module loop". Hence, it appears the only way to get info about baselines or to open baselines, is for the current version of the module to be open.